Skip to content

docs: correct lint/diff output examples and rule count in README - #119

Merged
davideast merged 2 commits into
google-labs-code:mainfrom
rmyndharis:docs/readme-accuracy-fixes
Jul 27, 2026
Merged

docs: correct lint/diff output examples and rule count in README#119
davideast merged 2 commits into
google-labs-code:mainfrom
rmyndharis:docs/readme-accuracy-fixes

Conversation

@rmyndharis

Copy link
Copy Markdown
Contributor

Summary

Three README accuracy fixes so the documented output matches what the CLI emits:

  1. lint summary key — the README shows "info": 1, but lint emits "infos". An agent parsing summary.info per the docs reads undefined. Corrected to infos.
  2. diff output shape — the documented example shows only colors/typography under tokens and omits the findings block entirely. The actual output (commands/diff.ts) emits all five token categories (colors, typography, rounded, spacing, components) plus findings: { before, after, delta } and regression. Updated the example to match.
  3. rule count — the table lists nine rules but DEFAULT_RULE_DESCRIPTORS registers ten; token-like-ignored (added in feat: warn on token-like frontmatter keys silently ignored by export #105) was missing. Added the row and updated "nine" → "ten".

Testing

Docs-only. Verified the rule list/severity against packages/cli/src/linter/linter/rules/index.ts and token-like-ignored.ts, and the diff/lint shapes against commands/diff.ts, commands/lint.ts, and utils.ts.

rmyndharis and others added 2 commits June 25, 2026 22:03
- lint `summary` uses the key `infos`, not `info`
- the `diff` JSON includes all token categories plus a `findings`
  block (before/after/delta) and `regression`; the example previously
  showed only two token categories and omitted `findings`
- the linter runs ten rules — add the missing `token-like-ignored` row
@davideast
davideast merged commit 6a879d7 into google-labs-code:main Jul 27, 2026
6 checks passed
@davideast davideast mentioned this pull request Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants